Integration request from AIML API - #7461

Completes the previous commit. `ApiProtocol` is exhaustively mapped in
several `Record<ApiProtocol, …>` tables, so adding the union member is
only half the change — the compiler names every table that still has to
answer for it, and each one is a real user-visible surface:

- suggested models: the flagships aimlapi.com marks hottest, so the BYOK
  dropdown opens on something useful rather than empty
- fast model: gemini-3.6-flash, for the memory extractor's auto pill
- protocol tab, label, key placeholder, and the console link that sends
  users to https://aimlapi.com/app/keys
- `ConnectionTestProtocol` and `MemoryExtractionProvider` in the contracts
  package, so the key smoke test and the memory extractor accept it

Verified: typecheck clean in all three packages — daemon, web, contracts.

Note for anyone repeating this: the daemon resolves
`@open-design/contracts` through `dist`, so a contracts source edit does
nothing until that package is rebuilt. The daemon's postinstall runs its
own tsc, which is where the two contract mismatches surfaced.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Both ids resolve, but openai/gpt-5.6-terra is the intended alias for the
suggested-model default; -pro is a separate, heavier SKU.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add aimlapi.com as a BYOK chat provider

The protocol tab was appended, putting it last in the picker while every
other table in the file already lists it first alphabetically. Moved to
the front so the ordering is consistent with the labels, placeholders and
console-link maps.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

List aimlapi.com first among providers

The 'aimlapi' protocol is already fully wired natively (state/apiProtocols.ts:
its own tab, suggested models, default model, labels, and a dedicated
providers/aimlapi-compatible.ts handler) — but KNOWN_PROVIDERS had no entry
for it, so defaultApiProtocolConfig()/switchApiProtocolConfig() couldn't
resolve a base URL when the aimlapi.com tab was selected in Settings: the
Base URL field fell back to empty/placeholder instead of prefilling
https://api.aimlapi.com/v1.

Adds that entry with protocol: 'aimlapi' (matching the existing tab id) and
a preferredModels list mirrored from SUGGESTED_MODELS_BY_PROTOCOL.aimlapi so
the two stay in sync.

fix: register aimlapi.com in KNOWN_PROVIDERS with the correct protocol

Registering aimlapi.com in Settings (KNOWN_PROVIDERS/BYOK_PROVIDER_PRESET_SPECS)
and daemon model listing wasn't enough to actually start a chat: the run
preflight in ProjectView.tsx and the daemon's OpenCode provider mapper both
enumerate supported BYOK protocols explicitly, and 'aimlapi' was missing from
both lists plus the shared ByokChatProtocol contract type. That made every
run treated as an unconfigured provider and bounced back to Settings even
with a valid, saved, tested API key.

- packages/contracts: add 'aimlapi' to ByokChatProtocol
- apps/daemon/runtimes/byok-opencode: map aimlapi to @ai-sdk/openai-compatible
- apps/web/ProjectView: recognize aimlapi in the BYOK run-preflight gate
- apps/daemon/provider-models: aimlapi model listing (Load models) support
- apps/web/state/config: surface aimlapi.com first in the BYOK provider grid

fix(aimlapi): recognize aimlapi.com as a supported BYOK chat protocol

Real BYOK chat runs through the OpenCode runtime, not the /api/proxy/*
routes: `streamMessage` — the web-provider dispatcher those routes exist
for — is called nowhere outside `providers/`, and ProjectView dispatches
`streamViaDaemon({ agentId: 'byok-opencode' })`. So the attribution pair
added with the provider only ever covered Test connection and model
discovery, while every actual inference request went out untagged.

That is the failure mode worth naming: nothing breaks. The chat works,
the connection test is green, and the traffic simply does not count.

`buildProviderEntry` hands `options` to the provider factory, which
forwards `headers` upstream, so the pair goes there. aimlapi.com now has
its own case rather than sharing the senseaudio/aihubmix one, since it is
the only one of the three that carries headers.

Also adds aimlapi to `usesAnthropicProxy`'s allow-list. Without it the
protocol falls through to the trailing baseUrl check and is treated as an
Anthropic proxy, which sends image attachments down the Anthropic path
for aimlapi.com users.

Test asserts the pair on the generated runtime config; confirmed it fails
when the headers are removed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Attribute the runtime that actually serves chat

Addresses the transcript-family review finding on
nexu-io#7461.

ProjectView stamps each API-mode assistant turn with
apiProtocolAgentId(config.apiProtocol) — 'aimlapi-api' for this tab —
and then sends the run through streamViaDaemon({ agentId:
'byok-opencode' }). scopeHistoryToAgent walks back from the latest user
turn and cuts the history at the first assistant turn whose agentId is
not in the target's family; isSameTranscriptAgentFamily resolves that
through the closed API_MODE_AGENT_IDS set, which 'aimlapi-api' had never
joined. AIHubMix hit the same seam and is already a member.

The effect is primary-path breakage for the feature this PR adds: from
turn 2 on, an aimlapi.com BYOK chat ships only the latest user message
and the model loses the conversation it just had. The new spec pins it —
against the unfixed code the transcript collapses to exactly
'## user\nmake the second step clearer'.

Also labels 'aimlapi-api' in AGENT_LABELS so the chat header shows the
provider instead of falling back to the raw agent id.